Crate holochain_integrity_types

Holochain Integrity Types: only the types needed by Holochain application developers to use in their integrity Zome code, and nothing more.

This crate is intentionally kept as minimal as possible, since it is typically included as a dependency in Holochain Zomes, which are distributed as chunks of Wasm.

This crate is also designed to be deterministic and more stable than the higher level crates.

Re-exports

• pub use action::Action;
• pub use entry::Entry;
• pub use kitsune_p2p_timestamp as timestamp;
• pub use prelude::*;

Modules

• action
• capability
  Capability Grants and Claims
• chain
  Source Chain Filtering
• countersigning
  Countersigned entries involve preflights between many agents to build a session that is part of the entry.
• dependencies
  Re-exported dependencies
• entry
  An Entry is a unit of data in a Holochain Source Chain.
• entry_def
• flat_op
  An alternative to [Op] using a flatter structure, and user-defined deserialized entry included where appropriate
• genesis
  Types related to the genesis process whereby a user commits their initial records and validates them to the best of their ability. Full validation may not be possible if network access is required, so they perform a “self-check” (as in “check yourself before you wreck yourself”) before joining to ensure that they can catch any problems they can before being subject to the scrutiny of their peers and facing possible rejection.
• hash
• info
  Information about the current zome and dna.
• link
• op
  Dht Operations
• prelude
  Common types
• rate_limit
  Rate limiting data types
• record
  Defines a Record, the basic unit of Holochain data.
• signature
  Signature for authenticity of data
• trace
  Types related to the debug host function
• validate
• x_salsa20_poly1305
• zome
  A Zome is a module of app-defined code which can be run by Holochain. A group of Zomes are composed to form a DnaDef.
• zome_io

Macros

• fixed_array_serialization
  Serialization for fixed arrays is generally not available in a way that can be derived. Being able to wrap fixed size arrays is important e.g. for crypto safety etc. so this is a simple way to implement serialization so that we can send these types between the host/guest.
• secure_primitive
  Cryptographic secrets are fiddly at the best of times.

Enums

• SecurePrimitiveError
  Errors related to the secure primitive macro.
• UnitEnumEither
  A full UnitEnum, or just the unit type of that UnitEnum

Traits

• UnitEnum
  A utility trait for associating a data enum with a unit enum that has the same variants.